PowerQuest Drive Image Professional Trial Version 2.01 Copyright (c) 1994-1998 PowerQuest Corporation. All rights reserved. U.S. Patent Nos. 5,675,769 and 5,706,472: other patents pending in the United States and elsewhere. PartitionMagic and PowerQuest are registered trademarks of PowerQuest Corporation in the United States and elsewhere; Drive Image is a trademark of PowerQuest Corporation. This version will run for 30 days after installation. This Trial version expires March 31, 1999. TABLE OF CONTENTS ----------------- 1. License Information 2. New User Interface Features 3. Image File Editor Improvements 4. Using Jaz, Zip and SyQuest Parallel Port Devices With a NetWare Client 5. Verify Disk Writes 6. List of ASPI Drivers and Supported Adapters 7. Compression Enhancements in Drive Image 2.0 8. If SyQuest Driver Fails 9. Access to CD-ROM Drive 10. Windows NT Server Issues 11. Hardware Configurations 12. Using Disk to Disk for Backup Purposes 13. Boot Manager Updated 14. Check for Extra Cylinder Switch 15. Disk-to-Disk Copy to Smaller Disk 16. Display Command Line Switches 17. Image File Integrity Checking 18. Creating a DOS Bootable Floppy from OS/2 or DOS 19. Additional Iomega Drivers Information 20. Additional SyQuest Drivers Information 21. Restoring Multiple Logical Drives 22. Delete Extended Partition 23. Windows NT Security Identifier (SID) 24. Installing under Windows 3.1 25. Image Files Appended on Creation 26. PowerQuest Newsletter 1. License Information ---------------------- For more information about the Drive Image Professional Version or Corporate, Government and Education license options, contact PowerQuest Large Account Sales at (800) 379-2566 or sales@powerquest.com. 2. New User Interface Features -------------------------------- The new Display Drive Information dialog in the Tools menu graphically displays the layout of the selected drive. The Browse file dialog has been enhanced to make file selection easier and to show image file comments and details. 3. Image File Editor Improvements --------------------------------- The Image File Editor can now restore selected files from a compressed and/or spanned Image file. Long file names are now supported. The user can now specify the maximum size of the files that make up a spanned Image. An internal index is created by the Image File Editor to accelerate file restore operations on compressed PQI files. To save the time required to regenerate this index each time the PQI file is accessed, it can be saved to a PQX file. When a compressed PQI file is selected the Image File Editor first looks for an existing PQX file. If found, it is read into memory and used to index the file. If it is not found, a new internal index is generated before file restore operations are permitted. 4. Using Jaz, Zip and SyQuest Parallel Port Devices With a NetWare Client ------------------------------------------------------------------------- Loading a parallel port device driver with a network client installed, may cause the system to hang. In order to successfully load the device driver for a parallel port drive, please reboot the system without loading the network client. This can also be done from the boot diskette set created by the install program. For additional help to resolve this problem, please contact your network administrator. 5. Verify Disk Writes --------------------- Disk write verification under Drive Image is disabled in order to speed up the process of creating and restoring hard-disk images. Disk write verification is not critical to safely create image files. If speed is not an issue, mark the Verify Disk Writes check box under Advanced Options if you want to enable DOS disk write verification. However, be aware that enabling disk write verification can slow the image file create process by as much as seven times. 6. List of ASPI Drivers and Supported Adapters ---------------------------------------------- Drive Image supports the following ASPI managers and cards: Driver/Bus Supported Host Adapter ============== ====================== ASPI8DOS.SYS ------------ PCI Bus Adaptec AHA-2910A/2910B Adaptec AHA-2930A/2930B Adaptec AHA-2940/2940AU/2940W/2940U/2940UW Adaptec AHA-2944W/2944UW Adaptec AHA-3940/3940U/3940W/3940UW Adaptec AVA-2904, AVA-2902E/I Adaptec AIC-7850/7855/7860/7870/7880 based SCSI host adapters Jaz jet (PC-only model) ASPI7DOS.SYS ------------ EISA Bus Adaptec AHA-1740/1742/1744 Adaptec AHA-1740A/1742A Adaptec AHA-2740/2742/2740T/2742T Adaptec AHA-2740A/2742A/2740AT/2742AT Adaptec AHA-2740W/2742W Adaptec AIC-7770 based SCSI host adapters VL BUS Adaptec AVA-2825 Adaptec AHA-2840VL/2842VL Adaptec AHA-2840A/2842A ASPI4DOS.SYS ------------ ISA Bus Adaptec AHA-1540B/1542B Adaptec AHA-1540C/1542C Adaptec AHA-1540CF/1542CF Adaptec AHA-1540CP/1542CP Microchannel Adaptec AHA-1640 ASPI2DOS.SYS ------------ ISA Bus Adaptec AVA-1502P/AP Adaptec AVA-1505 Adaptec AVA-1515 Adaptec AHA-1510/1520/1522 Adaptec AHA-1510A/1520A/1522A Adaptec AHA-1510B/1520B/1522B Adaptec AHA-1530P/1532P Adaptec AVA-1502AE/AI, AVA-1505AE/AI, AVA-1505AES Adaptec AIC-6260/6360/6370 based SCSI host adapters Adaptec AVA-1502AE/AI, AVA-1505AE/AI, AVA-1505AES PCMCIA Bus Adaptec SlimSCSI (APA-460 & APA-1425/50/50A/60/60A) MCAM18XX.SYS ------------ PCI Bus Adaptec AHA-2920/2920A MA160.SYS - If needed, please add to GUEST.INI or LDSQSCSI.BAT files. --------- ISA Bus Trantor T160 Microchannel Trantor T260 MA348.SYS - If needed, please add to GUEST.INI or LDSQSCSI.BAT files. --------- Parallel Port Trantor MiniSCSI Plus (T348) Adaptec MiniSCSI Plus (APA-348) MA358.SYS - If needed, please add to GUEST.INI or LDSQSCSI.BAT files. --------- Parallel Port Trantor MiniSCSI EPP (T358) Adaptec MiniSCSI EPP (APA-358) Adaptec MiniSCSI EPP (APA-358A) ASPIIDE.SYS ----------- IDE SCSI to IDE ASPI Manager Zip IDE drive ASPIATAP.SYS ------------ SCSI to ATAPI ASPI Manager ASPIPPM1.SYS and ASPIPPM2.SYS ----------------------------- SCSI to Parallel Port Zip Drivers Jaz Traveller ASPIEDOS.SYS ------------ Adaptec AHA-1740/1742/1744 (in Enhanced Mode only) ASPIPC16.SYS ------------ PC1600 adapter Zip Zoom SCSI Accelerator Adaptec APA-1460 and other AIC-6260/5360 based adapters Jaz jet ISA adapter Zip zoom SCSI Accelerator Zip Card PCMCIA SCSI adapter ASPI1616.SYS ------------ PC1616 adapter and other NCR-53C406A based adapters ASPI2930.SYS ------------ AHA-2930 adapter 7. Compression Enhancements in Drive Image 2.0 ---------------------------------------------- The Low compression method used in Drive Image 2.01 has been enhanced to allow restoration of individual files from an Image file. As a result, images created with Low compression using Drive Image 2.01 cannot be restored using Drive Image version 2.0 or earlier versions. Images created using Drive Image 2.0 can be restored by Drive Image version 2.0 and later versions. Images created with Drive Image 1.0 can be restored using Drive Image 2.0 and later. To create a compressed image using Drive Image 2.0 that can be restored using Drive Image 1.0, specify the /ZLB command line switch. This disables the enhanced compression used in 2.0 and forces the 1.0 compression method to be used. 8. If SyQuest Driver Fails -------------------------- If you receive the following message when loading your SyQuest removable drive: "Removable Drive(s) Not Found. See Readme for ways to correct this problem. Driver Not Installed." Please refer to the Additional SyQuest Drivers Information section in this file. If your SyQuest drive is a SCSI drive and is connected by an adapter not supported by the ASPI8DOS, ASPI7DOS, ASPI4DOS, ASPI2DOS, or ASPIEDOS, ASPI managers, see the list of supported adapters and edit the LDSQSCSI.BAT file to include the correct ASPI manager. 9. Access to CD-ROM Drive --------------------------- If you need to access your CD-ROM drive from Drive Image, you will need to add the command in the CONFIG.SYS file to load your CD-ROM driver and add the command in the AUTOEXEC.BAT file to load the CD-ROM extensions, for example, MSCDEX.EXE 10. Windows NT Server Issues ----------------------------- We have seen a Windows NT server try to cache the whole Image file in memory. With one or more clients on the network trying to restore images, the NT server fills up its RAM with the Image files. With very little RAM left to handle further requests, the NT server slows to a crawl. Microsoft technical support can not offer a fix and suggested that one put more RAM on the server. One can use the /MFS=100000000 switch to limit each Image file size to around 100 MB. This will help because each file is closed after moving to the next file and NT can re-use the memory cache. The NT server no longer tries to cache the whole Image file in memory. This is not an issue with NetWare servers. 11. Hardware Configurations --------------------------- Because of operating system conflicts that can result from different hardware configurations, Drive Image was not intended to copy or image a hard drive that will be used in a system with different hardware configurations. If you create an image on one machine and you wish to restore the image on a machine with a different configuration (e.g., motherboard, video card, etc.), the operating system may not boot correctly. Therefore, we recommend imaging and restoring to similar hardware configurations. 12. Using Disk to Disk for Backup Purposes ------------------------------------------ Drive Image now includes a hide/unhide feature that gives you the option of storing an exact back up of the existing operating system and application partitions on a second hard drive without causing drive letter conflicts. 13. Boot Manager Updated ------------------------ The Boot Manager is now updated during the restore operation. Partitions in an image file which were bootable from IBM's Boot Manager will now be bootable when restored. Previous versions would not boot if the starting sector changed due to a resize during the restore process. 14. Check Extra Cylinder Switch ------------------------------- The new /CEC command line switch checks for an extra cylinder. This corrects a problem of the BIOS and DOS reporting different maximum cylinder numbers. 15. Disk-to-Disk Copy to Smaller Disk -------------------------------------- You can now copy a partition or disk from a larger to a smaller partition or disk. The only restriction is that there be enough free space on the smaller destination to accommodate the used data on the larger disk. 16. Display Command Line Switches ---------------------------------- The new command line switch /? displays all available command line switches, their syntax and a short description. 17. Image File Integrity Checking ----------------------------------- The image file size is now double checked against the used data sector size. 18. Creating a Bootable Floppy from OS/2 or DOS ----------------------------------------------- To create a Bootable Floppy from OS/2 or DOS run the MAKEDISK.BAT file found on the CD in the OS2DOS directory. This batch command will create two diskettes. The first diskette is a DOS boot diskette. It also contains the removable media device drivers. The second diskette contains Drive Image. 19. Additional Iomega Drivers Information ----------------------------------------- Each time the Iomega driver program loads, it must also load an ASPI manager to communicate with the Zip or Jaz drive. The install program copies a large set of ASPI managers to the DRIVERS directory for SCSI, IDE, and Parallel Port interfaces. The Iomega driver program tries to load each ASPI manager until it finds one that allows it to talk to your drive. If it does not have to use this trial-and-error process to find the correct ASPI manager, it can load quicker. If you use only one or two specific host adapters, you may want to edit the GUEST.INI file and remark-out the ASPI managers you do not need. This will cause only the ASPI managers for the adapters you normally use to be loaded and tested. Use the following procedure to customize your GUEST.INI file: Step 1: Locate the GUEST.INI file in the DRIVERS directory where you installed Drive Image or on the floppy disk and open it using a text editor. This file is a text file, so you can use the Notepad in Windows, the DOS EDIT program, or any other ASCII text editor. Step 2: Identify the ASPI manager line the Iomega driver program needs to load to support your drive. For example, if you routinely use an Iomega PC1616 adapter, use the line that reads "ASPI=ASPI1616.SYS". The following table will help you identify the ASPI manager line you need to load: Iomega Adapter ASPI Manager ---------------------------- ------------ Jaz jet PCI (PC/Mac model) ADVASPI.SYS Jaz jet (PC-only model) ASPI8DOS.SYS Jaz jet ISA ASPIPC16.SYS Jaz Traveller ASPIPPM1.SYS Parallel Port Zip drive ASPIPPM1.SYS Zip zoom SCSI Accelerator ASPIPC16.SYS Zip Card PCMCIA SCSI adapter ASPIPC16.SYS Zip IDE drive ASPIIDE.SYS PC1616 adapter ASPI1616.SYS PC1600 adapter ASPIPC16.SYS Step 3: Remark out each ASPI manager line you do NOT need to load by inserting "rem " at the start of the line. For the example where the Zip or Jaz drive is connected to an Iomega PC1616 adapter, you would remark out all ASPI manager lines except the ASPI1616.SYS: rem ASPI=ASPIPPM1.SYS /INFO FILE=NIBBLE.ILM SPEED= 1 rem ASPI=ASPIIDE.SYS /INFO rem ASPI=ASPI8DOS.SYS /D rem ASPI=ADVASPI.SYS rem ASPI=ASPIPC16.SYS INFO ASPI=ASPI1616.SYS /SCAN /INFO Step 4: Save the changes to the GUEST.INI file and exit the text editor. Be sure to save the file as ASCII text or DOS text. NOTE: If you later need to use an ASPI manager which has been remarked out, simply edit GUEST.INI again and remove the "rem " at the start of the ASPI manager line. ASPI Manager Reference: Detailed reference information on the ASPI managers used by the Iomega driver program is located in the electronic "Installation Manual" (MANUAL.EXE). You can access the manual from the Iomega "Install" floppy for Windows/DOS by going to the DOS prompt and typing: A: MANUAL Assigning Specific Drive Letters for Iomega Drives -------------------------------------------------- To specify the first drive letter you want to use, add the "letter=" option to the command line. For example, "g:" will be assigned to the first drive it finds to support: GUEST.EXE letter=g If you have more that one Iomega drive, each additional drive will receive a drive letter following G in alphabetical order. (When supporting more than one drive, drive letters are assigned in order of SCSI ID number from lowest to highest.) More information can be obtained from the install diskettes that came with your Iomega drive and the Iomega web site. www.iomega.com 20. Additional SyQuest Drivers Information ------------------------------------------ There are 4 types of interfaces for SyQuest products, EIDE, EIDE Parallel Port (IEPP), SCSI and SCSI Parallel Port (SEPP). Each interface type requires a different driver or combination of drivers. The drivers may be loaded in either the CONFIG.SYS file or the AUTOEXEC.BAT file. To load drivers in the CONFIG.SYS file, list the driver in a device= command. For example: device=xxxxxx.SYS [switches] Where xxxxxx.sys represents one or more of the drivers described below and [switches] respresents optional driver switches. Most drivers accept the /d switch to display additional debug information. For example: device=xxxxxx.sys [switches] To load drivers in the AUTOEXEC.BAT file, use the SyQuest driver loader program, SQLOAD.COM. For example: sqload xxxxxx.sys [switches] Where xxxxxx.sys represents one or more of the drivers described below and [switches] respresents optional driver switches. For example: sqload epatsyq.sys /de sqload sqppdrvr.sys /s EIDE Driver ----------- The EIDE driver, SQATDRVR.SYS revision 1.89, supports the EIDE products SQ3105, SQ3270, EZ135, EZ230, SyJet, and SparQ. To load the driver in your config.sys file add the following line: device=sqatdrvr.sys /s EIDE Parallel Port Drivers -------------------------- The EIDE Parallel Port drivers, EPATSYQ.SYS revision 5.45 and SQPPDRVR.SYS revision 1.19, support the EZFlyer 230 and SparQ products. The EPATSYQ.SYS driver must be loaded before the SQPPDRVR.SYS driver in order to functional properly. To load the drivers in your config.sys file add the following lines: device=epatsyq.sys /de device=sqppdrvr.sys /s SCSI driver ----------- The SCSI driver, SQDRIVER.SYS revision 7.97, along with the ASPI manager for the SCSI adapter supports the SCSI products SQ44, SQ88, SQ200, SQ3105, SQ3270, EZ230, and SyJet. Many ASPI managers are included and are loaded to auto-detect the SCSI interface card. The ASPI manager must be loaded before the SQDRIVER.SYS driver in order to functional properly. To load the drivers in your config.sys file add the following lines: device=aspi8dos.sys /d device=sqdriver.sys /s SCSI Parallel Port Drivers -------------------------- The SCSI Parallel Port drivers, EPST.SYS revision 5.02 and SQDRIVER.SYS revision 7.97, support the SyJet parallel port product. The EPST.SYS driver must loaded before the SQDRIVER.SYS driver in order to functional properly. To load the drivers in your config.sys file add the following lines: device=epst.sys /de device=sqdriver.sys /s More information can be obtained from the install diskettes that came with your SyQuest drive and the SyQuest web site. www.syquest.com 21. Restoring Multiple Logical Drives ------------------------------------- Drive Image will create an extended partition large enough to contain all of the selected logical partitions in a single image file, and will create it large enough to hold these partitions if they have been manually resized or proportionally resized. Drive Image will not create an extended partition large enough to hold logical partitions restored from two different image files, since the extended partition is created at the time the first image is restored. In this case, the user can create an extended partition ahead of time with the Create Extended Partition option, and download the images in two separate steps. Because most operating systems do not support multiple, visible primary partitions, if you restore a logical partition to a primary partition slot, we recommend that you either delete or hide the partition if you encounter problems. Restoring multiple logical drive images can cause the drive letters of subsequent partitions to change, and that may make the computer fail to boot or cause applications to fail. For information on why drive letters change and how to fix them, refer to the HDINFO.PDF manual file in the ACROBAT directory. 22. Delete Extended Partition ----------------------------- The DELETE EXTENDED script command deletes the extended partition if it does not contain any logical drives. In earlier versions of Drive Image, the extended partition could only be deleted by a DELETE ALL command. 23. Windows NT Security Identifier (SID) ---------------------------------------- With Drive Image Professional, you can easily clone most operating systems for installation on other machines. Windows NT, however, provides a slightly greater challenge because of the NT Security Identifier or SID. Improperly cloning an NT workstation disk will result in another workstation with the same SID, causing an NT server conflict. For more information and to download a solution to the Windows NT SID problem, visit our web site at http://www.powerquest.com/downlwd/siddl.html. 24. Installing under Windows 3.1 -------------------------------- Installing Drive Image to Windows 3.1 or Windows 3.11 without a swap file will cause a GPF error during the installation. 25. Image Files Appended on Creation ------------------------------------ New Image files are always appended to any existing file data on creation. If you wish to create a new Image file insure that there is no existing file with the same name. 26. PowerQuest Newsletter -------------------------- PowerQuest has a monthly electronic newsletter that is dedicated to official announcements regarding PowerQuest Products. It also contains tips and techniques for getting the most out of your PowerQuest products. Signing up on the list will give you all the information you need regarding product tips, bugs, and patches. Just go to our home page (www.powerquest.com), enter your email address into the space provided and hit the "Sign me up" button. You will be e-mailed a response verifying your subscription.